Send print job module

In the Send Print Job module, the print job is sent to the device. You can set whether or not to send the print job encrypted (via IPPS) (remember that encryption and decryption take time).

A printer can also be entered in the module to which the printouts are always output. This is useful in a strictly direct-print workflow. In a print@me workflow, it might cause a print job selected on the device to be output on another device.

The module can occur several times in the workflow.

The placement of the module is not restricted. However, different effects result depending on at which points the module is used.

The Print Accounting Module

Print and hold module

Print All module

The module does not require any previous modules.

Successful: This is the module that is executed after the print job has been successfully transferred to the device.

Failed: This is the module that is to be executed if sending the print job to the device has failed. If this connection is not set, End module is executed automatically in this case. A useful option would be to route the print job to The Print Job List Module at this point (print@me jobs remain in the queue and direct prints are added to the queue).

If an error occurred while printing the job, users can be notified by e-mail. This is especially useful for direct printing (with print@me jobs, the user receives messages on the device).

Select how to send the print job to the device: Unencrypted using the standard TCP/IP port or encrypted using IPPS.

Hostname (or IP address) to which the print is always sent. A direct print can be realized in this way. Note that this hostname is also used if the print job was printed by print@me, meaning a print job selected on the device might be printed on another device.

If a print job cannot be sent (e.g., for a direct print, the device is turned off), the sending operation can be repeated. If this option is not activated, the error output of the module is executed immediately at the first failed send attempt. If this option is activated, the system tries to send the data for the time set under Maximum retry duration in the Retry interval. During this time, the print job has the status Printing... or, between the send attempts, the status Waiting and Resending. This can be viewed on another device with the Embedded Client or in the WebClient. Here you can also cancel the sending process and print the job on another device.

Retry interval: Specify here the time in seconds to wait between two transmission attempts.

Maximum retry duration: Enter the number of hours the transmission is to be repeated. The error output of the module is not yet executed for this time. This is only used if the maximum retry duration has elapsed without success.

This setting is only used when the print job cannot actually be sent, not, for example, when the print job cannot be output because the device cannot meet the requirements of the print job.

The DeviceService is responsible for the communication with the devices. It also generates page contents displayed on the device (visible interface of the Embedded Client). In addition, it carries out the licensing of the system and requires Internet access for online licensing. Its log file is Logs\DeviceService.log.

The print service accepts and analyses print jobs. It also checks the user rights when printing. It also sends the print data to the device. Its log file is Logs\PrintService.log.